Description

Moved extensions from the last item in parameters-col_name to the last item of parameters-col_description (after examples)

Motivation and Context

Extension fields that are part of a schema show up on the right hand column, but extension fields on parameters are under the left hand column. This tends to result in extensions of even moderate length either wrapping or expanding the name column unnecessarily. It would be more consistent (and cleaner) to have those extensions appear under the description.

How Has This Been Tested?

Built the change and visually verified with & without other fields (such as example & examples)

Screenshots (if appropriate):

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.